home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
HAM Radio 3.2
/
Ham Radio Version 3.2 (Chestnut CD-ROMs)(1993).ISO
/
tcp
/
nosmail
/
mbox_fwd.doc
< prev
Wrap
Text File
|
1990-11-07
|
9KB
|
214 lines
======== [31] ================================================================
Subject: NOS Mbox forwarding
From: From: klemets@sics.se
Date: Wed, 10 Oct 90 21:55:00 +0100
==============================================================================
The NOS mailbox now supports forwarding, both outgoing forwarding and
reverse forwarding. It keeps track of which bulletins have been
forwarded by adding "X-Forwarded-To:" lines to the messages. Messages
in public "areas" are sent as bulletins, with BID and everything.
Messages from private areas are treated as private mail and are
deleted after forwarding.
The message areas can be checked for messages to forward at a regular
intervals, which is set with the "mbox timer" command.
Forwarding can be started immediately with the "mbox kick" command.
There is also a "mbox motd" and a "mbox attended" command, which I
picked from the G1EMM code.
There is a new command in the mailbox too, "Verbose." It displays a
message with all it header lines, contrary to "Read" which only shows
four lines. It is also possible to read a message simply by typing its
number.
The mailbox reads a forwarding file, "spool/forward.bbs". Here is a
sample file:
sk0tm 0006
ax25 ax0 sk0tm
sk0tm
amsat
all
------
sm0rgv
netrom #sth675
.c sm0rgv-2
sm0rgv
amsat
The first word on the first line in a forwarding record is the name of
the BBS to forward to. This should be the same type of name which is
shown by the "mbox status" command. The second word is optional. It
specifies a range when forwarding may take place. "0006" means that
there will only be forwarding to this station between midnight and 6am.
The second line specifies how to establish the connection. It should
start with the protocol (ax25, tcp or netrom) and be followed by all
the parameters which are necessary when NOS has to establish a network
connection.
Directly after the second line there may be lines that start with a
dot. What follows after the dot will be sent to the remote BBS as soon
as the connection is established.
Then follows the names of a number of message areas, public or
private. Finally, there should be a couple of '-' signs to separate
one forwarding record from another.
The code seems to be working, although there could of course be bugs
left. Anyway, the source is available with ftp from sics.se. The
filename is archive/packet/ka9q/nos/mailbox.arc.
As usual, this message is the only documentation, so it could be worth
saving.
Anders
======== [01] ================================================================
Subject: NOS mbox forwarding
From: From: klemets@sics.se
Date: Fri, 12 Oct 90 16:07:56 +0100
==============================================================================
The latest version of mailbox.arc at sics.se dated October 12, 14:36,
contains some bug fixes, not only to the forwarding code but to the
general message handling mechanism as well.
Now there is support for what people call "hierarchical routing
designators."
The mailbox now understands its own "*** LINKED to" message...
It is possible to specify several time intervals in the forward.bbs
file. For instance: "w0xxx 0006,1212" means that there may be
forwarding to w0xxx whenever the forwarding timer expires from midnight
until 7 am, and from noon until 1 pm.
Anders
======== [12] ================================================================
Subject: Re: NOS Mbox forwarding
From: From: klemets@sics.se
Date: Mon, 15 Oct 90 11:56:41 +0100
==============================================================================
> Is there a way to send a message that is for a user at a bbs, rather than
> the bbs's owner? I can do it if I edit the .txt file in the mail directory
> to have the To: address I want, so my problem is how does one get a message
> for kb3kj @ w3ya to be placed in the w3ya mail area. There must be
> something I am overlooking.
When a message is entered to the mailbox, the address is rewritten
according to rules in the /spool/rewrite file. The first word on
each line in the rewrite file is an address using wildcards. If that
address matches the address you are trying to rewrite, it is rewritten
according to the format of the second word. If the third word is an 'r',
the rewrite procedure will be repeated, now using the new address as
input.
Ok, so here is a sample /spool/rewrite file for a machine with the
hostname sk0we.ampr.org:
*!* $2@$1 r
*@sk0we.ampr.org $1 r
*@*.ampr.org $1@$2.ampr.org
sm0rgv@* sm0rgv
*@w3ya* w3ya
*@k* $1%k$2%w3iwi.ampr.org@tomcat.gsfc.nasa.gov
The first line means that addresses written in the "host!user" format
should be rewritten to "user@host" and then the rewrite procedure
should be repeated.
The second line converts the address "user@sk0we.ampr.org" into the
local address "user" and then repeats the rewrite procedure.
The third line seems to do nothing. It just converts "user@host.ampr.org"
to "user@host.ampr.org". But it also exits the rewrite procedure
since the line does not end with an 'r'. Any address ending with
".ampr.org" will not be converted further.
The line "sm0rgv@* sm0rgv" will keep mail for sm0rgv on the local
machine even if it is mistakenly addressed to another BBS, such as
"sm0rgv@w3iwi". The line will however fail to convert addresses such
as "sm0rgv@w3iwi.ampr.org" because of the line described in the
previous paragraph.
The line "*@w3ya* w3ya" will leave mail for "user@w3ya" in the local
message area named "w3ya". The same goes for mail using some sort of
hierarchical routing designators such as "user@w3ya.state.na.us". The
only exception is for mail addressed to "user@w3ya.ampr.org" as
described above.
The line "*@k* $1%k$2%w3iwi.ampr.org@tomcat.gsfc.nasa.gov" is an
example of how to establish an Internet "wormhole." Suppose I want to
forward all mail to stations with callsigns starting with K to W3IWI
through the Internet. The line quoted above would do it. But if the
mail for "user@kxxxx" is received by w3iwi.ampr.org with SMTP, there
might be some problems because the rewrite file is not scanned when
mail is received with SMTP. This could easily be changed however. Let
me know if this is causing you any inconveniencies.
Anders
==============================================================================
Subject: Latest mailbox enhancements
From: klemets@sics.se
Date: Tue, 06 Nov 90 19:08:56 +0100
==============================================================================
The NOS mailbox now includes an SF command for forwarding a message
and an SR command for replying to a message.
This version also hopefully does not have the problems with mail file
locking that some of you have experienced recently. (I made those
changes a couple of weeks ago.)
I have also changed things so that the rewrite file is now scanned by
the SMTP server when messages are received, before the alias file is
scanned. This will allow you to send BBS-style addressed mail with
hierarchical routing desginators using SMTP.
The rewrite file is still scanned when a message is received
by the BBS. If the resulting address is local, ie. there is no
'@'-sign, the BBS will pass the message to the local SMTP server as
usual, but then the rewrite changes are not applied by the BBS. This
is to avoid applying the rewrite file twice, which could cause
unexpected effects.
The changed files are in archive/packet/ka9q/nos/mailbox.arc at sics.se
Have fun,
Anders
==============================================================================
Subject: more mailbox enhancements
From: klemets@sics.se
Date: Wed, 07 Nov 90 16:18:25 +0100
==============================================================================
I changed the mailbox code so that the new commands SF and SR only
work when a normal user executes them. If another BBS connects and
sends SR, that will still be interpreted as an attempt to send a
message of type R instead of the reply command. This will provide
compability with other BBSes.
If one uses NOS to forward messages between two MBL/RLI type BBSes,
one will discover that NOS has the annoying habit of adding
RFC-822 headers to every message, instead of the "R:" headers used by
the other BBSes.
I have solved the co-existance problem between RFC-822 and R: headers
in the following manner: RFC-822 headers are still added to all
messages received by the mailbox. When a message is forwarded to
another BBS, the RFC-822 header is normally included. But if this
message was received by forwarding from another BBS, however, it will
have R: header lines. In that case, the RFC-822 header is converted to
an appropriate R: line when NOS forwards the message.
The Read command will also digest any R: headers into a "Path:" line
in the same way other BBSes do. The Verbose command can be used to
view all header lines in full.
This makes this version of the mailbox fully comparable with any
W0RLI/WA7MBL/AA4RE BBS or MSYS. In general, NOS will have a lot more
features than any of these programs, as far as I can tell. Does
anybody know about some vital feature of MSYS that the NOS BBS is
still lacking?
Anders